Monster Media 1996 #15

home *** CD-ROM | disk | FTP | other *** search

/ Monster Media 1996 #15 / Monster Media Number 15 (Monster Media)(July 1996).ISO / bbs_misc / raptr9b4.zip / RAPUPD.DOC < prev next >

Wrap

Text File | 1996-06-22 | 50KB | 1,025 lines

RAPTOR BBS - Undocumented Commands (c) 1995, 1996 by The Raptor Development Team All Rights Reserved (6-28-95) The following additions and changes to RAPTOR have been made and are not at this time included in the document files. Multinode --------- RAPTOR BBS will now support up to 256 nodes under DesqView, OS/2 or other multitaskers. To configure the information for each node. (1) Start RAPTOR with the standard BBS.EXE. (2) From the WFC screen select <P> for system configuration, <A> for modem/node configuration then <A> for node number. (3) Enter the node number for the node you wish to configure, then proceed to enter the other information requested on the screen. (4) Return to the WFC screen after completeing all node information. (5) Repeat steps (2) through (4) for any other nodes. This will create the MODEM###.DAT file for each node. (6) Start each node with the command line BBS -n### where ### is the node number. If you use BBS without the -n### parameter RAPTOR will default to node 1. A new MCI code has been added to the doors MCI codes. %M will now pass the current Node number as a parameter to the command line in ONLINE.MNU. An MString of DOOR.BAT %M called from node 2 will then pass DOOR.BAT 2. A new MCI has also been added that can be used in files, prompts, and the string editor. An MCI of %E will display the current node number in the form 'NODE ###' where ### is the current node number. SysOp logs also now show the node number which the user is logged in on. Conferences ----------- RAPTOR now supports up to 26 conferences for message and file areas designated A to Z. All conferences are configurable with an ACS string to limit access to certain areas of the BBS. To assign a file or message are to a conference use the Cx ACS command in the area's ACS string, where x is the conference identifier. In other words an ACS string with the commands S100CD means Security level 100 and joined to conference D. The new menu Command Key to 'Join Conference' is OJ. If the MString for this command is left blank it will prompt the user for the conference they wish to join with an option to list the conferences. If the MString contains a valid conference Identifier then the OJ command will change the user to that conference. If the user is restricted from a conference by the conference ACS string they will not see that conference listed and will not be able to join that conference. The conference Editor is accessible from the WFC screen using the "$". The options in the editor are fairly straight forward to Insert a new conference, Modify an existing conference, or Delete an existing conference. (* Raptor will start using conference 'A' for each login, even though this conference has not been defined. The conference system allows you to make groups of message areas or file areas available to only users with certain security settings. *) This was changed in the .8 beta series to record the last conference the user was in. 'A' will be used for new users. Network Addresses ----------------- The addresses set up in the Network configuration are now used to configure the addresses in echomail message areas as well as in processing netmail by the RAPMAIL program. When you select the option to configure the network address of a message base you will see the list of addresses displayed and be prompted for which you wish to use. ============ <07-04-95> ============ Nonstandard Comports --------------------- Support for nonstandard IRQ's and Com Base addresses are supplied to RAPTOR through the fossil driver. However DSZ/GSZ and some other transfer protocols are interrupt driven and the fossil is unloaded by RAPTOR as it shells to the external protocol. In order for the protocol to handle the nonstandard port cofiguration it is necessary to pass the IRQ and base address of the comport to the protocol program. RAPTOR now allows you to configure the IRQ and Address of the port in the MODEM configuration menu from the MFC screen. These are passed to the protocol in the variable %I ( IRQ from modem congig) and %A ( base address from modem config). Refer to the documentation for the protocol driver you are using for the correct syntax to pass these variables to the protocol. You must then edit the protocol commandline in the PROTOCOL EDITOR from the WFC. ======== 07-08-95 ======== Mail processing ---------------- RAPTOR will exit with an errorlevel of 2 to DOS if there is new echomail or netmail. This will allow you to process mail only if there is new mail ( Yeah I know.... RAPMAIL is to ^$#&$* slow when the message bases get big... working on it <G>) instead of after every caller. The command line would look something like If errorlevel = 2 then goto newmail Goto Nomail :Newmail RAPMAIL -s REM Enter command sfor the processor here GEcho FMail etc. RAPMAIL -P GOTO END :NOMAIL GOTO END ========== 07-11-95 ========== RAPMAIL Scanning ------------------ RAPMAIL will now only scan the netmail directory and any echo areas with NEW messages. The purge will check all directories, if a .MSG or HIWATER.MRK file exists in that directory then it will be purged and the PURGING COMPLETE message displayed, or else the NO MESSAGES message will be displayed. This makes RAPMAIL much faster in normal operation. There is no change in the Toss operation. ========== 07/16/95 ========== Logoff Quotes ------------- Logoff quotes are now available to the users. To enable Logoff Quotes a new menu command "OQ" has been added. "OQ" will prompt the user if they wish to leave a logoff quote and allow them to enter a one line 78 character quote. There is NO MString for the "OQ" command, and the acs string may be set to restrict the users who have access to leave a quote. If you have 'AutoMessage in Logon' enabled inthe BBS setup the last logoff quote will be shown to the user in the form "(USERNAME) was logged in recently and said.." " <QUOTE>" Colors may be used in the quote line using the standard CTRL-P selections. If no color codes are used the quote will be in Yellow. The first line will be in Blue. The "OR" Command keys has also been added to allow users to read back through the logof quote file one screen at a time. "OR" has no MString for the command. Readmail commands ----------------- The read e-mail submenu commands have been changed to make them a bit more standard. To reread the last message use "A" for Again, and to reply use the "R" command. (*Public and Echomail currently still uses the "A" autoreply command... working on that one watch this space for future changes<G>*) **** All public and private messages now use 'A' to read again and 'R' to reply.***** ============= 08-15-95 ============= Expanded RIP features --------------------- The RIP support for your users is still being updated.Mouseable pop-up picklists for File Areas, Message Ares, and Conferences is in place. The RIP background wallpaper behind the lists is configurable. RAPTOR will look for a .RIP file for each area WPMSG.RIP for messages WPFILE.RIP for files WPCONF.RIP for conferences and display this file as the background for the pop-up lists. If the file does not exist RAPTOR will display it's own internal wallpaper. These files must be stored in the AFILES directory. It is recommended that theses screens contain no mouse areas, and that after creating these files you use a text editor to remove the |#|#|# (RIP_no_more) command from the end of the file. The editor RIP control panel and the file browse control panel and RIP login prompts are all internal to RAPTOR and will be configurable in future releases through the RIP cfg options to be added, but will not be editable. External Full Screen Editor ---------------------------- Although RAPTOR includes a very powerful internal editor, it still has the drawback of being a line based editor. Since many users prefer the ease of using a full screen ANSI editor we have included support for RemoteAccess (RA (c) Wantree Development and Andrew Milner) style full screen external editor. We have so far tested this feature with the shareware editor IceEdit ((c) Jeremy ). A new option (X) has been added to the system configuration menu to configure the external editor. Options here are A. Use external editor B. Editor dropfile type C. Editor command line A). This is a yes/no toggleable field which enables use of an external editor. If this is set to NO then RAPTOR will not attempt to use an external editor. B) This is the drop file tpye needed by your external editor. When you select B you will be presented with a list of possible drop file types and their corresponding key letter. For IceEdit we selected type 'D' - Dorinfox.def. Selecting '-' will not create a drop file allowing you to pass the values required by your editor to it on the command line using the standard RAPTOR Door information MCI codes. C) This is the command line required to start your editor. In configuring IceEdit we entered a command line of: EDIT.BAT %M ^ ^ | |_____Passes current node number for this node | (i.e. Node 1 would pass 1) | |________Batch file to launch your editor Our EDIT.BAT was really pretty simple CD\ICEEDIT ICEEDIT /D:C:\RAPTOR\TEMP\N%1 CD\RAPTOR The /D: switch in the ICEEDIT parameter passes the directory to look for the drop files to the door (DORINFOx.DEF and MSGTMP). The %1 batch variable passes the current node number from the %M MCI code making the N%1 come out as N1 ( default directory for node 1 from the Modem config setup) In order to properly configure an external editor you must understand a bit about how RAPTOR handles messages. If you are replying to a message RAPTOR creates a file called MSGTMP and stores it in the node drop file directory for the current node. This directory is configured in the modem setup option from the system configuration menu of the WFC. MSGTEMP is a file which contains the text of the message you are replying to. This file is used by RAPTOR's internal editor as the quotable part of the text, and is also used by RA compatible editors as their quote files. It is necessary to point the editor to the proper directory where it can find MSGTMP. In this case both the Dorinfox.def file and MSGTMP are located in the same directory, and ICEEDIT assumes they will be found together, so the /D: switch points ICEEDIT to the proper directory for both it's drop file and the MSGTMP quote file. ICEEDIT will rewrite the MSGTMP file to include the selected quoted text as well as the text of the new part of your message. If you abort the message in ICEEDIT the MSGTMP file will be erased. If RAPTOR returns from the external editor and MSGTMP does not exist it will assume the message has been aborted. If MSGTMP exists RAPTOR will then import the text into the mesage base. It is not necessary to enter the To and subject information in the editor, only the message body text. That, in a nutshell, is how to install your external editor. As with all shareware products, please register any shareware editor you may select. If a user is in either the external OR internal editor it is not possible to do an on-line adjustment of their account status using the F1 key. Other stuff ----------- Although the recent dates of the additions to this file make it look as if we have been sitting on our backsides for a couple weeks that isn't exactly true. Many changes have been begun internally for added features and options. In the near future we will see the ability to attach files to E-Mail, configure the look of on-the-fly RIP screens, have your default RIP menus updated automatically whenever you change your .MNU files, and hopefully the addition of on-the-fly light bar menus for your ANSI users. ============ 8-17-95 ============ Automatic updating of default RIPs ---------------------------------- Ok as mentioned above some of the near future has arrived. The default RIP menus are now generated whenever a RIP caller logs on. The screens will show only the commands the user has access to. To control the function of the updater a new switch has been added to the system config <H> Miscelaneous menu. That option is 'Use default RIP menus'. If this is set to ON then RAPTOR will regenerate a new RIP menu anytime you change the .MNU file. If the menu is all first commands there will be no RIP screen generated. >>*<< >>*<< >>*<< >>*<< >>*<< >>*<< >>*<< >>*<< IMPORTANT!!! If you use custom RIP screens be certain to set the option to use default RIP menus to OFF! If this option is enabled your custom screens will be overwritten by the default menus! >>*<< >>*<< >>*<< >>*<< >>*<< >>*<< >>*<< >>*<< Configuration for colors and text styles in a future release will be added shortly... RIP menus will also accept only 48 commands, in other words command #49 and #50 will NOT be shown on the default RIPS. Of course if you have that many commands on one menu it is probably long past time to create a submenu <G> =========== 8-28-95 =========== Split screen chat ----------------- With the Version 06a2 release RAPTOR introduces the concept of external software modules. Modules allow 3rd arty developers to write RAPTOR specific utilities whic can run as an external program, and have RAPTOR pass the necessary information to the Module in a standard format. Some of the parameters are still under development, however we introduce our first Module with this the release, the Split Screen Chat Module. The module is contained in the file CHATMOD.EXE, and unlike door style chat programs require absolutely NO SysOp configuration. In addition thrid party authors can develop a split screen chat module which SHOULD require no configuration on the sysop's part. Provided the executable is called CHATMOD.EXE this file can be copied into the Main RAPTOR BBS directory and run exactly as the Development team supplied module. Split screen chat may be accessed with the ALT-C key combination and the standard line by line chat is still accessed by the F-10 keys. The Module Concept ------------------ The module concept allows third party developers to write addin programs or modules which can be run seamlessly from RAPTOR and require little or no SysOp installation. In order to qualify as a module a program must meet these requirements. 1) Modules will NOT make use of any form of drop file other than those created by RAPTOR when the 'Launch Module' command is called. 2) Modules must read the RATOR files necessary to locate directories as described in the RAPTOR Development Kit. In other words, if the Module requires access to one or more of RAPTORS Message or File Bases the module must read the RAPTOR STATUS.DAT file and the other appropriate files to locate the path to the files, and may use external configuration files ONLY for information not supplied by RAPTOR. 3) The Module must detect the fossil used by RAPTOR automatically, and handle initializing the fossil if using Fossil IO or make certain that it can use it's own onternal comm routines. It must NOT be up to the sysop to configur comm information. 4) The module must contain file locking routines or be clearly marked for SINGLE NODE USE ONLY. 5) The module should only modify files created by RAPTOR for module purposes only. It should modify RAPTOR'S data files directly ONLY if the information needed is not available through the rereadable module data file. ***NOTE*** The final format of the Module Data File has not been completely finalized. The final spec for this will be available shortly. For up to the minute information about what is included in the information available to modules contact the Development Team. In addition, in order for a module to be considered "approved" it should meet the following crieria: 1) If the module is shareware then the registration fee should be reasonable when compared to the priceof RAPTOR. In other words a $40.00 file handler for a $60.00 BBS is not considered reasonable <G>. The development team will make every effort to supply basic utilities and modules that are not internal to RAPTOR available to sysops at a free or EXTREMELY inexpensive rate. 2) When unregistered the module may have features disabled but must present a true representation of the modules MIAN function. Nags are permitted either at the beginning of the module or the end, but NOT both, and the nag should NOT exceed 15 seconds in length. This area should also include any author/copyright info, again at the beginning or end, not both. 3) By accepting a module for 'approved ' status, the development team does not gharantee that any one module will get exclusive rights to 'approved'stsus for that type of module, nor that we will not at some future date include similar features either internally or in the form of a free module. IOW if you write a killer QWK module, we may still release a basic QWK module. 4) The author of approved modules must subscribe or have access to a BBS that does subscribe to one of the current RAPTOR support echos( as of now NVR_NET and SAC_NET). We will not support your product! Also the development team must have a current voice phone number to contact the author of any approved modules. Failure to provide support on a reasonable basis will be reason to drop a products 'approved' status. 5) Continued acceptance of a product as approved is entirely up to the discretion of the development team. Any product may be dropped from the approved list at any time for any reason. Although some of these requirements may sound a bit restrictive, their basic purpose is in keeping with The Development Teams basic mission statement. To provide the BEST possible online Host system to system operator, for the best price possible, requiring the least amount of configuration possible, while maintaining maximum flexibility. While we are not attempting to tell anyone how to write his/her program, or how to price or market his/her program, these requirements are presented only as guidelines for the things we will evaluate before adding a module to the approved list. Certain approved products may be included with releases of RAPTOR, in their shareware form. Shareware products submitted for evaluation to be included as approved should include both a shareware and a registered version. 11-15-95 ======== Ver 0.7a1 OK well it's been a while since we worked on this doc, but here is the latest. A few minor cosmetic fixes, and a few bug fixes in RAPMAIL (now v0.5) The bugfixes include eliminating tossing those silly arcmail packets created by your front end mailer back into your BBS mail<G>. Also fixed some problems RAPMAIL had finding users with netmail. Now tosses netmail to the right user account instead of the first one with a partial match to the name (oooops!) In RAPTOR itself changed the YES/NO prompts to a toggleable type prompt. Hit a key to toggle the hilight from yes to no then hit enter... ANSIBOXES --------- Ansiboxes will draw a 3-D box around one line of text. This option is selectable from the miscelaneous configuration menu. At present there are three types (0= No box, 1= Blue Box, 2= Gray Box) More colors to follow. Use of the boxes is accessible to sysops using a new MCI code @I%string to print%. This MCI is available in both files and messages(example title lines for your bulletins) as well as in the string editor for prompts etc.. You are restricted however to using only 76 characters in the 'string to print' The two '%' signs are required in the MCI code... Split screen Chat ----------------- Split screen chat now behaves exactly like the line style chat as far as use of time goes. This is internal to RAPTOR so will behave like this with ANY chat module written to use with RAPTOR. File Browsing ------------- The 'B' Browse Files command now displays one screen then the prompt rather than a pause. This allows users to tag after each screen is displayed. This method is preferable to the 'L' List files command. We suggest eliminating the default List Files and renaming the Browse command to List. This seems to make it easier for the users... 1-4-96 ------ INTERNODE PAGING and TELECONFERENCE ==================================== 1) New Menu Commands- 'OD'- Page a user on another node from the menu prompt. Do not need to be in teleconference area to use this. No Mstring. 'OT'- Enter teleconference area to access conference rooms, group chat etc. 'OW' -Who's on line listing. Shows activity for ANY nodes which have been active. 2) New configuration options- (Key sequences are from WFC) 'PB5'- Sets the path where the internode chat files will be located. At installation this path defaults to 'LOGS'(old 'trap'). For optimum speed this could be set to a RAMDrive 'PEM'- If on enables checking for internode messages. If off no internode commands are available and no internode files are created. Single node systems should NOT enable the teleconference system. 3) Commands from teleconference submenu '/J [Conference #]' - Join conference room # '/A [Username] {actionword]'- Transmits action word string inserting your name and Username in appropriate places.(Not yet implemented) '/P [Username] [Message]'- Sends page message to Username wherever they are in the BBS, provided they are available for page. '/ [Username] [Message]'-Whispers a message to Username. In other words noone else in the conference room will see this message. '/$' - Displays users information. '/#' - Who's on line. '/X' or 'X' - Exits Teleconference area. '/?' or '?' - Displays Teleconference help screen. It is important to realize that teleconferenceing is a very disk intensive operation and that signifigant speed improvements can be realised by using a ramdrive for the teleconference file path. The Teleconference files are relatively small, so the Ramdrive would not have to be very big. 1-2 K per node would be more than sufficient.( The files are actually 414 bytes each, but the 1 to 2 k would allow for small files to be attached.) Right now there is no way for a user to toggle chat availability, that will be coming shortly. OS/2 NOTES!!!!! ----------------- When running under OS/2 it is necessary to DELETE the VOLUME ID from your hard drive. The reason is a quirk in OS/2 which returns the volume label as a filename. During the logon procedure RAPTOR checks to confirm that all files in the temp dirs have been deleted from the previous caller. If OS/2 Returns the Volume Label RAPTOR will try to delete a file with that same name, since the file doesn't exist a very sudden and unpleasant crash will result. We are looking into ways to eliminate this problem completely, however we offer this idea as a temporary solution. Besides.... what good does the bloody Disk Label do anyway!?!?!?!?!?!?! Passing actual speeds --------------------- Two new MCI codes to pass the actual connect speed to either a door on the command line or to a protocol ( example CEXYZ allows passing both the locked port rate and the actual connect speed, also some CD rom doors need the actual speed to calculate correct download limits.) The actual speed is passed to either a door or an external protocol by using the %S MCI code. Example: 14,400 bps modem with a locked port at 19,200. For a 2400 baud caller %B will pass the value 19200 while %S will pass the value 2400). 2-7-96 ------- OK if you've made it to this point, be certain that you now(if not before) read the README!!.1ST file. This contains some additions not discussed in this document. ( Now aren't you glad YOU aren't the doc coordinator<G>) ================ File Listings ================ A lot of the recent activity has gone into cleaning up the file listing appearance, both for new scans and using the List/Browse option. First of all if you have any comments or suggestions on the looks of the display forward them to one of the development team. Version 8b4 introduces sysop selectable file list types. The three options are: Option #1 --------- Num Filename Size FilePts Short Desc Long desc Long desc .... for the length of the long desc Option #2 --------- Num Filename Size File Pts Short Desc You will notice option 2 has no long description and will display 15 files per screen. Option #3 --------- Num Filename # of DL's U/L Date Uploader Size Fiel pts Short Desc Long desc Long desc ..... till the end of long desc If no option has been selected in the system config ( From the WFC screen P,F,L for the file list style option) then option #3 will become the default. This can be changed at any time. Again any suggestions for improvements in this area are more than welcome, and all will be considered. ================= 2-11-96 ================= Configurable netmail path ------------------------- Begining with the .8b4 release the path for your netmail *.MSG directory is now configurable. You MUST fill in this path and run RAPMAIL.EXE Dated after 2-10-96(v.7b) for this to be used. The path is set from the network configuration (from the WFC P,I ) as option J. This should be the full path to your netmail directory. ================== 2-20-96 ================== Messsage base display files --------------------------- Raptor can display a custom RIP/ANSI/MSG file when the user READS messages in a message base. Simply create a file named MDF#####.* where the ##### is the number of the message where this file should be displayed (NOTE:Message base #1 would be MDF1.ANS for an ansi file. Do NOT pad out the number with 0's) and place it in the MISC (AFILES) directory. Thios file will be displayed when the user selects the READ option, it will not display during scans of the message areas. ================ 3-7-96 =============== OK several things finalized today, simple things first... Total system callers -------------------- You can now edit the total number of system callers from the configuration editor in the Miscellaneous Configuration Area (from the WFC select 'P' then 'H'). Use this however you want <BEG>. This was primarily designed in the event that the STATUS.DAT got corrupted and had to be replaced. Personal Message Scan --------------------- RAPTOR will now scan the public message areas for messages addressed to the user. This is similar to the Newscan in that it can be global or single base, can scan across all conferences, and uses the same MString as the newscan. The difference is the user is prompted as to whether RAPTOR should update their Hi-Read message pointers after the scan. Selecting NO at this prompt will NOT update the pointers allowing the user to come back and read all new messages at a later time. Implementation can be done two ways. A new Menu Command has been added 'MY' which will take the user to the personal newscan. Also a toggle is provided to prompt the user during logon to scan for new personal messages. The menu command will use an MString if provided, however the logon sequence will behave as if no MString was found, prompting the user if it should be global. Menutitle MCI codes ------------------- Two new MCI codes are provided which contain the menu title lines 1 and 2. %] - returns title line 1 of the current menu %[ - returns title line 2 of the current menu These are primarily designed to allow creting ansi prompts for menus which can be displayed using the %J@filename@ MCI code. Multi - menu configuration --------------------------- *********************************************** BEFORE PROCEEDING, BE CERTAIN TO BACKUP YOUR STATUS.DAT AND STRING.DAT FILES!!!!!!! IT IS ENTIRLEY POSSIBLE TO DESTROY THE DEFAULT PATHS STORED IN STATUS.DAT. IF YOU GET AN ERROR MESSAGE THAT PATHS ARE MISSING SIMPLY REINSTALL YOUR BACKUP OF STATUS.DAT AND TRY AGAIN ************************************************ OK well since we haven't documented the language file and string editor yet we'll start from the very beginning. RAPTOR's string editor will also create a language.dat file in your DATA(GFILES) directory. If this file is present, it will create an on the fly menu prompting the user to select a language. Also contained in this file is a number corresponding to the paths to be used by RAPTOR for the *.MNU menu command files as well as the path for the RIP/ANSI/MSG display files for this language. OK now what does this all mean? It means simply you can create a language with the look and feel of any other BBS software, right down to duplicating the command keys a user would enter if using that software. Let's say there is a BBS package called PussyCat, and you want to duplicate it's looks (WHY?? I dunno!). But you would create a language which duplicated the prompt strings for that software, then you could create a set of RIP/ANSI screens to duplicate the looks of that software, and then even create a set of *.MNU files to change the normal RAPTOR command keys for anyone who chooses that Language! OK now to rough out the ideas here. These are the basic rules... 1) If there is a language.dat file you MUST create a MEUNCFG.DAT file by using the Alternate Path Editor (from the WFC select P then J). This will prompt you for the set to configure, and prompt you for the paths for the *.MNU files and the RIP/ANSI files. 2) Several languages can share the SAME Paths for MNU and display files, even if the langauge files themselves are different. The menu set is selected in the string editor. 3) You should ALWAYS make menu set 1 the default MENUS path and default MISC path (or what you specified during RAPINIT). Use these files with your 'default' language file. 4) The MENUS dir and the MISC dir for each language must BOTH exist and have the appropriate files in them if you want to use either one. In other words if you want to use the MNU files for all languages, but different RIP/ANSI/MSG screens you must copy the MNU files to the appropriate MENU directory for that set. Note though, that the MENUS path can be set to the default menu path. Just be certain that the MENUS path you setup does in fact exist. 5) The max number of Languages is 20 as well as the max number of menuset directories. Make sure the directories shown in the config (from the WFC P then B ) are used also as the directories for the #1 menuset. Hopefully by now you have the BASIC idea, but to really appreciate the power of this sytem you will need to play with it. A couple things to think about.. 1) You don't have to start from 'scratch'. Copy your original MENUS and MISC files to the new ones and modify them. 2) Create custom menu prompts using the same filename and the %J MCI code with the two new Menu title MCI's. This allows you to make the prompts all different. 3) I would suggest creating directory names MENU1, MENU2 , MISC1, MISC2 etc. just to make it simpler on you to maintain these directories. As you can see this allows almost complete configuration of not only the look but the feel of your RAPTOR BBS! These changes require some getting used to. We suggest creating one language, and pointing it to the #1 menuset. This will allow you to configure all the strings for this language. After the strings are done and your menus and display files are finished, use the string editor to change the menu set used by that language to the correct one. Editing menus- If you are using multiple menu sets, RAPTOR will prompt you for the menuset to edit when you enter the menu editor. If the paths specified for the MENU and MISC directories for this menu set do not exist, RAPTOR will attempt to create them. If the menus already exist then RAPTOR will load the MNU files from the MENU dir for that language. Be aware that menu sets are referred to by NUMBER not the language name since several languages can all share the same menu set directories. It is possible to have 20 languages, and only one MISC and MENUS dir, with all languages using the same menu set. Whew! Hopefully this is enough to get you started. As a precuation ******* BACKUP YOUR STATUS.DAT!!!!! BEFORE YOU BEGIN TO EDIT THE MENU SETS!!!!!! ******* ######################## HOT TIP!!! ######################## In the message and file newscan routines you can now play a couple games with RAPTOR!. To achieve the 'classic' TG/RG scrolling scan messages use these lines as the newscan began and newscan done strings in the string editor. NEWSCAN BEGAN - [Newscan - %Y ] %W messages began%M NEWSCAN DONE - [Newscan - %Y ] DONE! %M %M notice the %M MCI Codes ( carriage return) and particularly the double %M on the done string. To have RAPTOR NOT scroll the display, but simply overwrite the previous message on the same line use these lines. NEWSCAN BEGAN - Scanning - %Y - %W messages NEWSCAN DONE - Notice the DONE string is left BLANK! ( no space, just hit enter when the cursor is in the first position of the empty input window) and that the BEGAN string does NOT have the %M MCI code. ########################### Qoute Headers -------------- RAPTOR now adds quote header lines in the stringeditor. Information from the message being quoted can be passed in the following MCI's. These are valid ONLY in the 2 quote header lines. The quote headers are used in public posts, and if the string is left blank for either line it is not used... ~A = From who ~B = To who ~C = Message date and time ~D = Message title --------------------------------------------------------------------------- ============= 3-23-96 Version 9b2 ============= Internal Call back verifier --------------------------- RAPTOR now includes an internal call back verifier. When RAPTOR validates a user by Call back it will set their account to the levels you specify in the call back validation level(from the WFC P,G). --------------- Configuring CBV --------------- RAPTOR CBV system allows the SYSOP to configure the way the CBV functions under several conditions. In the CBV configuration section (from the WFC P,S) the following options are available. Call back new users- Will force all new users who meet other restrictions to be sent through the call back verifier. The other way to validate users is to set the verifier up through the menu system using the 'OE' command keys. Call back local only- This will call back local phone numbers in the three digit exchange areas you specify in CALLBACK.DAT, located in your RAPTOR/DATA(GFILES) Directory. This is an ascii text file which can be created with DOS edit or any other text editor. Each three digit exchange number is entered on it's own line in this file. Call back my area code- this will call back users in all exchanges provided the area code field of the users number matches the are code of the BBS phone number field (from WFC screen P,B). This will ignore any entries in the CALLBACK.DAT file. Call back all (LD)- This will call all users back in ANY area code, appending a '1' in front of any numbers not in your AREA CODE. Hang up after callback- This will disconect the user after they have been validated, showing them a message that they have in fact been validated and asking them to call the BBS back. Controlling the CBV from the local keyboard -------------------------------------------- The ESCAPE Key will abort ALL attempts to validate the current user. The SPACEBAR will abort the current dial attempt to validate the user. Normally the CBV will make 3 attempts to contact the user. Once the user answers the phone by typing ATA when they see ring on their screen and the modems negotiate a connect, the user will have three attempts to enter the correct password. If the password is correct they will have three attempts to enter their correct phone number. If either of these fails the call is terminated. All CBV activity is appended to the sysop log showing both successes and failures. Also the users name, handle, password, phone and city are appended to the log as a new user enters their information. This will allow you to check for any attempts to enter bogus info or use things like the %PW lockup routines that work in other software<G> The CBV includes default text that is displayed to the user before he is called back and upon successful connection to his terminal This text may be replaced by RIP/ANSI/MSG files called CBV1.??? and CBV2.???. CBV1 is diplayed to the user just before disconnect when RAPTOR is preparing to call them back, and CBV2 is diplayed immediately after successful connect. RAPTOR uses the ANSI password and phone prompts from the string editor to prompt the user for their info. The CBV also stamps the date the user was validted in the user record date validated field. ----------------------- User Expiration ----------------------- RAPTOR also includes a user validation expiration function. Anytime you validate a user (ALT-V on-line or '*' from the user editor or via CBV) the current date is entered in the Date validated field of the user record. There is also a field in the record for the number of days until the users validation expires. This is normally set to zero, and is set by the sysop for the number of days until this user's validation level expires. The third field used in the expiration routine is the level to expire to. Level 1 = New user level Level 2 = Call back validated level Level 3 = Validated user ( ALT-V or '*') this option is for any users you manually validate above one of three defined levels. Selecting the date validated field within the user editor will stamp the users account with the current date. When the user logs on if their days to expiration is set to anything other than zero, RAPTOR will compare their validation date with the current date and if the difference is greater than days to expire then their account will be reset to the Level to Expire to. ---------------- Newuser Letter ---------------- A text file (NEWLETR.MSG) located in the MISC(AFILES) directory will be shown to all first time callers as an Email message. Use the %H MCI code to pass the user's name to the message. This mail will be automatically deleted when the user hits RETURN, Q, or D at the prompt. (These are the only valid inputs accepted at the prompt); This file can contain Pipe color codes, and MCIs. The name used in the from field for this letter comes from the first line of NEWLETR.MSG. The actual message body text begins with line 2. This allows the sysop to send the New User Letter with either his real name or handle. ------------------------------------------------------------------------ ---------------- File Lists ---------------- Improved the logic of the 'List' Files (Browse) command so that RAPTOR checks the length of the long description of the following file. If the complete description cannot be displayed on the current screen the prompt will be shown and the file shown on the next screen. This should eliminate the occasional scrolling problem and the truncated file descriptions in the .8beta series. Also added a Yes/No question for the user to select whether they want to see the long description.... that and a few cosmetic improvements improve the looks and flexibilty of the file displays... ---------------------------------------------------------------------------- RAPTOR 9b3 05-05-96 ____________ Mass Uploads ------------ RAPTOR now includes an option to 'Mass upload' files. When using the /U upload all files, you will be prompted whether to mass upload files. A mass upload will not prompt you for descriptions for the file. It will upload a blank short description, and use the FILE_ID.DIZ for the long description if it exists. If no FILE_ID.DIZ exists then RAPTOR will insert a description line stating no description is available. ----------- CD-ROM Uploads ----------- If a file base area is marked with the 'C'(CDROM) flag, RAPTOR will search the download path for a text description file ( such as FILES.BBS) that is specified in the FILE configuration( from the WFC 'F') option 'M' is the file name or the description file, and option 'N' is the position in the description line where the actual description text will start. When searching for the matching filename, RAPTOR assumes the filename starts at character 0 of the line. The description will be entered for the short description, and if a FILE_ID.DIZ is found this will be used for the long description. If the description file for the area is not found in the same directory as the downloadable files, the path to the description may be placed in the Upload path of the file base configuration. This will prevent you from having a hard drive upload area for this CD area. ---------------- Upload event --------------- Running BBS -U will do a mass upload for all file directories. This can be convenient for uploading files from a network file distribution area. This is an automated event which will upload all files in all directories, using the FILE_ID.DIZ for the extended description, and a blank short description. ------------------ Old user deletion ------------------ Running BBS -D will dlete users who have been inactive for a specified number of days. The number of days is configured in the main configuration(from the WFC P, D, option T) This will delete the users account, all mail to or from this user, and any short messages for this user. It will not pack the user base, and will honor accounts with the DO Not delete Flag set. ================ RAPTOR 9b4 ================ 6-16-96 Final Beta release ------------------ Current plans call for the release of 9b4 to be the final public BETA of RAPTOR before the release of the full 1.0 version. It is with deep regret that we have accepted the resignation of Michael Keefe of Tombstone Software as senior programmer for the development team. Mike has made many signifigant contributions to RAPTOR in the last 18 months, not only in code but also in ideas. The upside of this situation is it allows me a bit more flexibility in issuing bugfixes, since we don't have to maintain two current versions of the code 500 miles apart<G>. Hopefully when Mike has more time he will be able to return to the development team. In the meantime I expect we will se several third party utilities for RAPTOR released by Tombstone ( hint hint Mike!). Current commitments to work and college have just put too much strain on Mike's time. The prerelease special price of $30.00 will expire July 31, 1996. Any orders for RAPTOR at this special 50% off price must be postmarked no later than midnight July 31, 1996. BEAT KEY evaluation codes will no longer be valid after the release of 1.0. The QWK functions will not be fully implemented on systems running the BETA KEY. QWK pkts will be limited to 25 messages on unregistered sites and sites running BEAT KEY registrations. RAPMAIL ------- RAPMAIL now marks netmail as RECEIVED when it is processed. Messages -------- Color codes in messsages are now added when the messages are read as opposed to when they were written or imported by RAPMAIL. This allows ANSI files to be displayed in the message body without those annoying heart-code colors buried in the first line... QWK Mail -------- The QWK Mail functions are now in place and functional. Total messages per packet are limited to 40 messages in this version. The 9b4r version will be released to registered sysops only and has unlimited QWK packet size. Currently the WELCOM/GOODBYE screen options and the New message file lists are not functional, these will be included in the 1.0 release. Configuration is pretty self explnantory. Here are the menu commands which control the QWK areas. QO - Configure the users QWK options Default archiver Pack messages sent by the user Include WELCOME/GOODBYE screens ( nonfunctioanl in this release) Include new files list ( nonfunctional in this release) Delete E-Mail after it is downloaded Mark Public messages as read after downloding QS - Select message bases to include in QWK scan. This can be different from the areas scanned while the user is reading on-line. QD - Download a QWK packet. This scans the selected messsage bases, packs the messages, and downloads the packets to the user. ( For local packets you must drop to DOS and move the packet from the node dropfile path to a directory for reading. QU - Upolad a REP packet. This uploads the user's REP packet, unpacks it and imports the messages to the message bases. For a local REP before using this caommand move the REP packet into the node drop file path. Netmail messages are not currently supported in .REP packets. Finally you must insert an 8 characetr BBSID name in the miscellaneous configuration option (P,H,I from the WFC) This is the 8 characetr which will be used for the filename for QWK/REP packets, as well as the BBSid to be used by the QWK reader and RAPTOR's .REP processor to validate the origin/destination of the packets. This field does not need to be 8 characters. The 8 character limit is the max limit. For example here at the Eagle's Lair our BBSID is LAIR, thus producing LAIR.QWK and LAIR.REP. ------------ 06-20-96 ------------ Added integrity check to files attached to EMail. This will use the integrity check command line from the archiver setup for the type of archive used in the attached file. If the integrity test command line is set to use THDPRO or another virus scan program then the file will be scanned. If the file is found to be beinfected the virus scanning software ( again we recommend THDPro to control the scan) should be setup to move infected files to another directory. RAPTOR will NOT control this. Your virus scanning software MUST be able to handle infected files on it's own.....